Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e329736d7efc22c587449d9a730624d2955acf301809b8b7f90b3b525789f8

Tx prefix hash: 4396251ff07457f80c14a9064a34c4a4e5df95ceea2d64c065ce9110f4dd5a37
Tx public key: ebe3f78571295d4ab6ed0a603ada91a134353f86f62afe9fe63ae2f4161a18ce
Timestamp: 1737413348 Timestamp [UCT]: 2025-01-20 22:49:08 Age [y:d:h:m:s]: 00:149:18:52:03
Block: 1201726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106787 RingCT/type: yes/0
Extra: 01ebe3f78571295d4ab6ed0a603ada91a134353f86f62afe9fe63ae2f4161a18ce0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f0adde602882f30c4e56a1616247e08e64c35400cb627f66a1331c1faa83b7c 0.600000000000 1688383 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": 1201736, "vin": [ { "gen": { "height": 1201726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f0adde602882f30c4e56a1616247e08e64c35400cb627f66a1331c1faa83b7c" } } ], "extra": [ 1, 235, 227, 247, 133, 113, 41, 93, 74, 182, 237, 10, 96, 58, 218, 145, 161, 52, 53, 63, 134, 246, 42, 254, 159, 230, 58, 226, 244, 22, 26, 24, 206, 2, 17, 0, 0, 0, 3, 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