Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8708e4ae370bd884a9b93a5e4a9c9fa3eeccd4d65ca92a32d457b2bc88ec2f9

Tx prefix hash: 0fc1ad49f95ed80c2fbea0106f7e8bebdd05c85ba95d9ef431dc98ccbbed292c
Tx public key: 10cd019c0b1f1700a544841b4330a676cef3976a5a06a60c919bcdcb308d0aa9
Timestamp: 1713783024 Timestamp [UCT]: 2024-04-22 10:50:24 Age [y:d:h:m:s]: 01:191:18:02:14
Block: 1006018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395690 RingCT/type: yes/0
Extra: 0110cd019c0b1f1700a544841b4330a676cef3976a5a06a60c919bcdcb308d0aa902110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1beece71219d8ad251d35c0c8eb39c41149ea268bb51c15a2e2c05419f260677 0.600000000000 1466902 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": 1006028, "vin": [ { "gen": { "height": 1006018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1beece71219d8ad251d35c0c8eb39c41149ea268bb51c15a2e2c05419f260677" } } ], "extra": [ 1, 16, 205, 1, 156, 11, 31, 23, 0, 165, 68, 132, 27, 67, 48, 166, 118, 206, 243, 151, 106, 90, 6, 166, 12, 145, 155, 205, 203, 48, 141, 10, 169, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 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