Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4bba1643739c0a917267a72f36e7749e3a8fa1d18abff75d65f38b62dcf2a0d0

Tx prefix hash: 88047bcf2b22ca6b86752caf5648061ad9775ecc9d78805692540216e93be00a
Tx public key: a045982cd5d4561d9ae1bbf0db8f87b42fe87af4d40278fa0aaad7d6e80ef060
Timestamp: 1698196918 Timestamp [UCT]: 2023-10-25 01:21:58 Age [y:d:h:m:s]: 01:159:04:09:22
Block: 877012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374756 RingCT/type: yes/0
Extra: 01a045982cd5d4561d9ae1bbf0db8f87b42fe87af4d40278fa0aaad7d6e80ef06002110000000233af99f4000000000000000000

1 output(s) for total of 0.762246074000 dcy

stealth address amount amount idx
00: af1a9f040807b2bab6b442ce1cfc284b521749aed969db487ebc6fb0d54876c2 0.762246074000 1332370 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 877022, "vin": [ { "gen": { "height": 877012 } } ], "vout": [ { "amount": 762246074, "target": { "key": "af1a9f040807b2bab6b442ce1cfc284b521749aed969db487ebc6fb0d54876c2" } } ], "extra": [ 1, 160, 69, 152, 44, 213, 212, 86, 29, 154, 225, 187, 240, 219, 143, 135, 180, 47, 232, 122, 244, 212, 2, 120, 250, 10, 170, 215, 214, 232, 14, 240, 96, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8