Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c1855dd0c67d13239c3c7a35352041fbd63ef02e214d1718aa3381ede97233a

Tx prefix hash: d35bb962445f8649756bc3722ef9c743f108be1b660f32e69ac5afc32d5a9d09
Tx public key: 67c04357bbb7c08d4ecc75a7ae35de385f5b6843eda33b5f0791f59a847a3d00
Timestamp: 1719633443 Timestamp [UCT]: 2024-06-29 03:57:23 Age [y:d:h:m:s]: 00:344:00:42:56
Block: 1054513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245880 RingCT/type: yes/0
Extra: 0167c04357bbb7c08d4ecc75a7ae35de385f5b6843eda33b5f0791f59a847a3d000211000000030cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5651f21c8722df2c2d760feb92a512e6081f373d3816f2a7827998dc0e03c7 0.600000000000 1524876 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": 1054523, "vin": [ { "gen": { "height": 1054513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5651f21c8722df2c2d760feb92a512e6081f373d3816f2a7827998dc0e03c7" } } ], "extra": [ 1, 103, 192, 67, 87, 187, 183, 192, 141, 78, 204, 117, 167, 174, 53, 222, 56, 95, 91, 104, 67, 237, 163, 59, 95, 7, 145, 245, 154, 132, 122, 61, 0, 2, 17, 0, 0, 0, 3, 12, 206, 6, 54, 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