Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b4b000a1d577f9a5d77e90edadf5ea33c3b4548bc593773fd1ae9fda36e2e9

Tx prefix hash: a48c80ccc4212ae2c1199dafe36c0c35ef19eb0f9f44b035263c997d325611f8
Tx public key: ee132c7d8f46199c61414f172dc11263f40b1190770039634e14fca4122ab154
Timestamp: 1698381903 Timestamp [UCT]: 2023-10-27 04:45:03 Age [y:d:h:m:s]: 02:010:23:08:16
Block: 878550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527395 RingCT/type: yes/0
Extra: 01ee132c7d8f46199c61414f172dc11263f40b1190770039634e14fca4122ab1540211000000034b8f5122000000000000000000

1 output(s) for total of 0.753354109000 dcy

stealth address amount amount idx
00: 1ddc35e4701e0eb811c599cde2ca9bf0181df0ce35956ab2dd580b77d8f710f5 0.753354109000 1334002 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": 878560, "vin": [ { "gen": { "height": 878550 } } ], "vout": [ { "amount": 753354109, "target": { "key": "1ddc35e4701e0eb811c599cde2ca9bf0181df0ce35956ab2dd580b77d8f710f5" } } ], "extra": [ 1, 238, 19, 44, 125, 143, 70, 25, 156, 97, 65, 79, 23, 45, 193, 18, 99, 244, 11, 17, 144, 119, 0, 57, 99, 78, 20, 252, 164, 18, 42, 177, 84, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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