Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ff172c6f7bda34938e253f919d3542039f81df448a3a4265ad3e55999bcc405

Tx prefix hash: facd4449db8897617ebef0392e671dfc2516bce8bfc5e20b71dbb8fa9e69ef88
Tx public key: ad092fa39f8c5b8286be5a1fa1a57a0a776bd6e83d05eda9edb14d57a5adeecd
Timestamp: 1702055748 Timestamp [UCT]: 2023-12-08 17:15:48 Age [y:d:h:m:s]: 01:196:06:11:38
Block: 908784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401274 RingCT/type: yes/0
Extra: 01ad092fa39f8c5b8286be5a1fa1a57a0a776bd6e83d05eda9edb14d57a5adeecd021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 792977dc1b589d37b8949345ddf2bca9fe5bd1ca221b5dcef0970df43d3642f4 0.600000000000 1365839 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": 908794, "vin": [ { "gen": { "height": 908784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "792977dc1b589d37b8949345ddf2bca9fe5bd1ca221b5dcef0970df43d3642f4" } } ], "extra": [ 1, 173, 9, 47, 163, 159, 140, 91, 130, 134, 190, 90, 31, 161, 165, 122, 10, 119, 107, 214, 232, 61, 5, 237, 169, 237, 177, 77, 87, 165, 173, 238, 205, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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