Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a23e8afdea9ebe5af10bcbb428aaee46f3b01f5b599b731c297a02e2985fec4

Tx prefix hash: 040166c4c93a433dfbad171cf7c0fd42fc5ff4e07b61beb613fd76c21b187fa5
Tx public key: 6fc4aa325e2ae38775504adf5c740bd2e208c940522ac23798508d36527df91b
Timestamp: 1702659963 Timestamp [UCT]: 2023-12-15 17:06:03 Age [y:d:h:m:s]: 01:036:15:52:31
Block: 913790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287518 RingCT/type: yes/0
Extra: 016fc4aa325e2ae38775504adf5c740bd2e208c940522ac23798508d36527df91b02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a0d16df9c2351191d831eaedfa53eee50817c199cb5439f8ae7f2347bb596b 0.600000000000 1371068 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": 913800, "vin": [ { "gen": { "height": 913790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a0d16df9c2351191d831eaedfa53eee50817c199cb5439f8ae7f2347bb596b" } } ], "extra": [ 1, 111, 196, 170, 50, 94, 42, 227, 135, 117, 80, 74, 223, 92, 116, 11, 210, 226, 8, 201, 64, 82, 42, 194, 55, 152, 80, 141, 54, 82, 125, 249, 27, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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