Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab8eb1f7da892541966fd1c53cfb3cb5ecc9ae3e16322dd320c7ffdb590d7c28

Tx prefix hash: d1d3c6cf2c407826b2f523801b15b8501265b5ef936423248f098c37bb7edabd
Tx public key: dcbc2d772ca81d50dc987b21ee79442760e90a3e79d722df0ba014c118d4eca4
Timestamp: 1683354396 Timestamp [UCT]: 2023-05-06 06:26:36 Age [y:d:h:m:s]: 01:345:18:15:10
Block: 754007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508348 RingCT/type: yes/0
Extra: 01dcbc2d772ca81d50dc987b21ee79442760e90a3e79d722df0ba014c118d4eca4021100000001e7ace25d000000000000000000

1 output(s) for total of 1.948327691000 dcy

stealth address amount amount idx
00: 1e9f7f74628813e724e99dfe41be5a0db09b77a2e7ae08e0fec6217988c6db85 1.948327691000 1202252 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": 754017, "vin": [ { "gen": { "height": 754007 } } ], "vout": [ { "amount": 1948327691, "target": { "key": "1e9f7f74628813e724e99dfe41be5a0db09b77a2e7ae08e0fec6217988c6db85" } } ], "extra": [ 1, 220, 188, 45, 119, 44, 168, 29, 80, 220, 152, 123, 33, 238, 121, 68, 39, 96, 233, 10, 62, 121, 215, 34, 223, 11, 160, 20, 193, 24, 212, 236, 164, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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