Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4891782f4d11b8a82cae0ae41a0dcf3ba3d02a36c280fdbec9ef98d7dac924

Tx prefix hash: aa73e4b0777db7a6ac13e3f7416a702e5f74174b5c53f8a5abfbad5901ca4b4f
Tx public key: 6bbe9715d80e2166c66178549fa657e08348065bb19d4421da89b40c4a1abdd1
Timestamp: 1590432671 Timestamp [UCT]: 2020-05-25 18:51:11 Age [y:d:h:m:s]: 04:339:00:46:55
Block: 103240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168270 RingCT/type: yes/0
Extra: 016bbe9715d80e2166c66178549fa657e08348065bb19d4421da89b40c4a1abdd1021100000170d2466498000000000000000000

1 output(s) for total of 279.205379064000 dcy

stealth address amount amount idx
00: a68ebe8bb035c81a26547f8ceb7146d6dd6177da9c46caebf662a5ccdc78f994 279.205379064000 181141 of 0

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": 103250, "vin": [ { "gen": { "height": 103240 } } ], "vout": [ { "amount": 279205379064, "target": { "key": "a68ebe8bb035c81a26547f8ceb7146d6dd6177da9c46caebf662a5ccdc78f994" } } ], "extra": [ 1, 107, 190, 151, 21, 216, 14, 33, 102, 198, 97, 120, 84, 159, 166, 87, 224, 131, 72, 6, 91, 177, 157, 68, 33, 218, 137, 180, 12, 74, 26, 189, 209, 2, 17, 0, 0, 1, 112, 210, 70, 100, 152, 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