Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17b06dbcd35bf6d9c9040571f5219fe14b09bad1e64859e73a1468d7b49719c3

Tx prefix hash: a32d914964a108e35c86b699e639a2e56e99a4b3dfa9a99218ad177b8ef042fd
Tx public key: 628552b5e8c12ce0a919ead37fd2e7ef8be58e1d21daec802890f3050b96d70a
Timestamp: 1713152961 Timestamp [UCT]: 2024-04-15 03:49:21 Age [y:d:h:m:s]: 01:056:11:32:14
Block: 1000769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301377 RingCT/type: yes/0
Extra: 01628552b5e8c12ce0a919ead37fd2e7ef8be58e1d21daec802890f3050b96d70a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6eb6d408b4f7de0ccffe7b32772a2672477710124e29f897b2105b488c1a349 0.600000000000 1461269 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": 1000779, "vin": [ { "gen": { "height": 1000769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6eb6d408b4f7de0ccffe7b32772a2672477710124e29f897b2105b488c1a349" } } ], "extra": [ 1, 98, 133, 82, 181, 232, 193, 44, 224, 169, 25, 234, 211, 127, 210, 231, 239, 139, 229, 142, 29, 33, 218, 236, 128, 40, 144, 243, 5, 11, 150, 215, 10, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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