Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2dd4404b66087eea06c6cd48e7d3fdf66a3df8689c407125a14d8998128e25c

Tx prefix hash: 8bc877d2996a4a0b7436a280aa644d7273234a20c328d02b9cba987f1ebe826a
Tx public key: b602e8ef80adcdfc2961758efecddb912bf9568b19b692a878b21c5606dd60d2
Timestamp: 1719406323 Timestamp [UCT]: 2024-06-26 12:52:03 Age [y:d:h:m:s]: 01:135:22:07:45
Block: 1052625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355698 RingCT/type: yes/0
Extra: 01b602e8ef80adcdfc2961758efecddb912bf9568b19b692a878b21c5606dd60d202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d3634620121ef82273c30fbeadee1d7e588aa424b3e068e8691aa0da0b8d8b 0.600000000000 1522956 of 15

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": 1052635, "vin": [ { "gen": { "height": 1052625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d3634620121ef82273c30fbeadee1d7e588aa424b3e068e8691aa0da0b8d8b" } } ], "extra": [ 1, 182, 2, 232, 239, 128, 173, 205, 252, 41, 97, 117, 142, 254, 205, 219, 145, 43, 249, 86, 139, 25, 182, 146, 168, 120, 178, 28, 86, 6, 221, 96, 210, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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