Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bdfb8bea78b6feda9cc46eff775f2f228d4e13bf4d2922e878fa83dadd14c33

Tx prefix hash: f615d59d781b7bcf8f7dbc8d6d1b8d81c922e84eca1ec17fd41e21171569eb68
Tx public key: 3a9d1b779913694cf97a647d899c199f6e715e34692d464075c96744f25a26cd
Timestamp: 1737243726 Timestamp [UCT]: 2025-01-18 23:42:06 Age [y:d:h:m:s]: 00:057:02:09:34
Block: 1200327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40618 RingCT/type: yes/0
Extra: 013a9d1b779913694cf97a647d899c199f6e715e34692d464075c96744f25a26cd0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f084e5e2e6b817f8e638b2ce8e8a3215a14c6258f4312958f53f98548925eea 0.600000000000 1686970 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": 1200337, "vin": [ { "gen": { "height": 1200327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f084e5e2e6b817f8e638b2ce8e8a3215a14c6258f4312958f53f98548925eea" } } ], "extra": [ 1, 58, 157, 27, 119, 153, 19, 105, 76, 249, 122, 100, 125, 137, 156, 25, 159, 110, 113, 94, 52, 105, 45, 70, 64, 117, 201, 103, 68, 242, 90, 38, 205, 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