Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d04312bce2eed2042bd381087d889a696c4028c7cb20a15b1f60def73238bf

Tx prefix hash: 1b9792da2013c55a69faec5e44ef24240d4406fd4a18c5d19d6f8a9c514a6d84
Tx public key: 2a7259b4746d8d67ee1e442b8a88b8482359b8361cfe1d626f6929469edfb384
Timestamp: 1738011954 Timestamp [UCT]: 2025-01-27 21:05:54 Age [y:d:h:m:s]: 00:045:18:53:06
Block: 1206482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32748 RingCT/type: yes/0
Extra: 012a7259b4746d8d67ee1e442b8a88b8482359b8361cfe1d626f6929469edfb3840211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc69e66e7cbb5b96fdaab7d1b13cf107683d87298ad0679fd1fb782a2145bc3f 0.600000000000 1693191 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": 1206492, "vin": [ { "gen": { "height": 1206482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc69e66e7cbb5b96fdaab7d1b13cf107683d87298ad0679fd1fb782a2145bc3f" } } ], "extra": [ 1, 42, 114, 89, 180, 116, 109, 141, 103, 238, 30, 68, 43, 138, 136, 184, 72, 35, 89, 184, 54, 28, 254, 29, 98, 111, 105, 41, 70, 158, 223, 179, 132, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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