Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21af6c1837e20103be6510fb15947b44bf7ed873908744fb66b4f90eb407cf83

Tx prefix hash: 3bc9d56617a154a52290ee52bdaef587ba41b3a0a0a38c53bdfdb7b97ae65596
Tx public key: 0f2d4a525c8320a5a7c27821fd7f277186650b97a76a0d000cdfe963273db001
Timestamp: 1714344655 Timestamp [UCT]: 2024-04-28 22:50:55 Age [y:d:h:m:s]: 01:049:14:19:55
Block: 1010667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296307 RingCT/type: yes/0
Extra: 010f2d4a525c8320a5a7c27821fd7f277186650b97a76a0d000cdfe963273db00102110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84e933c8af4b1e8e223e291d318f9d67b657e6a0519a474a64b392a7fea6b038 0.600000000000 1472685 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": 1010677, "vin": [ { "gen": { "height": 1010667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84e933c8af4b1e8e223e291d318f9d67b657e6a0519a474a64b392a7fea6b038" } } ], "extra": [ 1, 15, 45, 74, 82, 92, 131, 32, 165, 167, 194, 120, 33, 253, 127, 39, 113, 134, 101, 11, 151, 167, 106, 13, 0, 12, 223, 233, 99, 39, 61, 176, 1, 2, 17, 0, 0, 0, 8, 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