Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aabbdef6919b47362c187d926243cad360ca88acf435d1b8f9087243416b7ab

Tx prefix hash: dffedc86b1bf2164f05f2ece3c7c1d32d8a25b5ef36b183ae0ce4471f2581224
Tx public key: 3837e0e81740af00d54a7436f3c94c0a60437fb2a925f2dd6b53a579530ccc8b
Timestamp: 1661490444 Timestamp [UCT]: 2022-08-26 05:07:24 Age [y:d:h:m:s]: 02:248:10:47:20
Block: 574007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698807 RingCT/type: yes/0
Extra: 013837e0e81740af00d54a7436f3c94c0a60437fb2a925f2dd6b53a579530ccc8b021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.692661533000 dcy

stealth address amount amount idx
00: 4d2a8b8a658e494f433aa9f65b1a07e66490800e8b2ccf6b24ca5cf13d389f0e 7.692661533000 1007311 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": 574017, "vin": [ { "gen": { "height": 574007 } } ], "vout": [ { "amount": 7692661533, "target": { "key": "4d2a8b8a658e494f433aa9f65b1a07e66490800e8b2ccf6b24ca5cf13d389f0e" } } ], "extra": [ 1, 56, 55, 224, 232, 23, 64, 175, 0, 213, 74, 116, 54, 243, 201, 76, 10, 96, 67, 127, 178, 169, 37, 242, 221, 107, 83, 165, 121, 83, 12, 204, 139, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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