Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e6151e4ed3db7b674bb01e393b8b65f9582542b33342ff0d19a6f1211f370c

Tx prefix hash: 96501e3432b20286c8978709fa405a86e7ec1e328fdcee60b48b8e326f9168d6
Tx public key: f03fa1dd233ae28a3f3b6dcdaabd3e4f00577e4c52ea0ec2fb69d34e566ef833
Timestamp: 1703619742 Timestamp [UCT]: 2023-12-26 19:42:22 Age [y:d:h:m:s]: 01:342:21:26:47
Block: 921754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503937 RingCT/type: yes/0
Extra: 01f03fa1dd233ae28a3f3b6dcdaabd3e4f00577e4c52ea0ec2fb69d34e566ef83302110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 747a2a136db3f9d67ce4e8a39c331a014a9df2d11aa5a8d73d28efcc180a23fd 0.600000000000 1379448 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": 921764, "vin": [ { "gen": { "height": 921754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "747a2a136db3f9d67ce4e8a39c331a014a9df2d11aa5a8d73d28efcc180a23fd" } } ], "extra": [ 1, 240, 63, 161, 221, 35, 58, 226, 138, 63, 59, 109, 205, 170, 189, 62, 79, 0, 87, 126, 76, 82, 234, 14, 194, 251, 105, 211, 78, 86, 110, 248, 51, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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