Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 619ec3bcce47c834b8bc3a4cbfb21a2b747ce5dfb0a435e0d7fd14bcbe4ed1c7

Tx prefix hash: fe6e8da64db14485ae3ac8e82396a31bc33fcacba3f6db2f9c4e0494ef75e80a
Tx public key: 79a553e39151f829b3d61c44cddcebdcc3b8e6f9b787583ad20fd78fe3a0e15d
Timestamp: 1738392590 Timestamp [UCT]: 2025-02-01 06:49:50 Age [y:d:h:m:s]: 00:335:07:09:22
Block: 1209607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237474 RingCT/type: yes/0
Extra: 0179a553e39151f829b3d61c44cddcebdcc3b8e6f9b787583ad20fd78fe3a0e15d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dcaa154774cfc9b270986fad9288a5dc8f0d6ec9d641262f72d1e573d9852c2 0.600000000000 1696352 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": 1209617, "vin": [ { "gen": { "height": 1209607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dcaa154774cfc9b270986fad9288a5dc8f0d6ec9d641262f72d1e573d9852c2" } } ], "extra": [ 1, 121, 165, 83, 227, 145, 81, 248, 41, 179, 214, 28, 68, 205, 220, 235, 220, 195, 184, 230, 249, 183, 135, 88, 58, 210, 15, 215, 143, 227, 160, 225, 93, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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