Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ee07e7cf6f057a6691dcb46e646c79e790cfb557e24ccc013fc37d1b88e483

Tx prefix hash: fef1057ea5339f0c9e3cb6b1eb955e3cd15f77847fd14200d8122e822465cc68
Tx public key: d98c21989bf03b58fe27a3be54688b03ae9c2f8cf928e89829c9ae991e42270e
Timestamp: 1704014030 Timestamp [UCT]: 2023-12-31 09:13:50 Age [y:d:h:m:s]: 01:143:00:46:38
Block: 925014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363379 RingCT/type: yes/0
Extra: 01d98c21989bf03b58fe27a3be54688b03ae9c2f8cf928e89829c9ae991e42270e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71f509b35af5a9bdc624dfb83cc0d7f6aa1ad9546d6869931a46f1b3af2535c7 0.600000000000 1382774 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": 925024, "vin": [ { "gen": { "height": 925014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71f509b35af5a9bdc624dfb83cc0d7f6aa1ad9546d6869931a46f1b3af2535c7" } } ], "extra": [ 1, 217, 140, 33, 152, 155, 240, 59, 88, 254, 39, 163, 190, 84, 104, 139, 3, 174, 156, 47, 140, 249, 40, 232, 152, 41, 201, 174, 153, 30, 66, 39, 14, 2, 17, 0, 0, 0, 4, 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