Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab7a495944929426f8673b951b6d65db8a2c1a173c0e96fcca955e511e915e22

Tx prefix hash: bc82425f67169a75875db2147f245bccc188e7e8bae70678a12babe46af0f7a4
Tx public key: f9586229d50b365df04206fa40b1f4855abdd37f8a658563d2ef1fd65aa5cadb
Timestamp: 1725031668 Timestamp [UCT]: 2024-08-30 15:27:48 Age [y:d:h:m:s]: 00:238:16:04:14
Block: 1099266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170446 RingCT/type: yes/0
Extra: 01f9586229d50b365df04206fa40b1f4855abdd37f8a658563d2ef1fd65aa5cadb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3c9f1ae902aec83b01326028e8e647be26022102fbf2df48e1e5ea9dec73ce 0.600000000000 1575221 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": 1099276, "vin": [ { "gen": { "height": 1099266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3c9f1ae902aec83b01326028e8e647be26022102fbf2df48e1e5ea9dec73ce" } } ], "extra": [ 1, 249, 88, 98, 41, 213, 11, 54, 93, 240, 66, 6, 250, 64, 177, 244, 133, 90, 189, 211, 127, 138, 101, 133, 99, 210, 239, 31, 214, 90, 165, 202, 219, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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