Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abdcf2a9e4e342c01b38630d1f1f02cf0136d6afb5192fdf7ee605977326508

Tx prefix hash: 9fd1c706feb2728e3299bffbe8d1af81cbe9fd4ce1ef0906e4c0e894cc727c32
Tx public key: bc98b94eea1828fb8a0830a296bece8fcce716df7e171450ab217d793f31dffe
Timestamp: 1709215199 Timestamp [UCT]: 2024-02-29 13:59:59 Age [y:d:h:m:s]: 01:255:10:43:51
Block: 968148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441298 RingCT/type: yes/0
Extra: 01bc98b94eea1828fb8a0830a296bece8fcce716df7e171450ab217d793f31dffe02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a9e1a17f4d3d41cdcd06994c7202cad1fa3158289c25b39836b17ef4dfe4549 0.600000000000 1427947 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": 968158, "vin": [ { "gen": { "height": 968148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a9e1a17f4d3d41cdcd06994c7202cad1fa3158289c25b39836b17ef4dfe4549" } } ], "extra": [ 1, 188, 152, 185, 78, 234, 24, 40, 251, 138, 8, 48, 162, 150, 190, 206, 143, 204, 231, 22, 223, 126, 23, 20, 80, 171, 33, 125, 121, 63, 49, 223, 254, 2, 17, 0, 0, 0, 10, 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