Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fda0e733f8ca44311d54ba1d266aaf7f7150e2173ebd00c2fbb118052554a7c3

Tx prefix hash: 964b184af4883f12911c1183b046e65af5c1b4d6e181597035b322e17c6e8f6a
Tx public key: 0bf236fc5753f0f5fa895dc053383beb090321e1fc940fa6eb9311f54d46ee32
Timestamp: 1738955210 Timestamp [UCT]: 2025-02-07 19:06:50 Age [y:d:h:m:s]: 00:357:09:00:03
Block: 1214275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253085 RingCT/type: yes/0
Extra: 010bf236fc5753f0f5fa895dc053383beb090321e1fc940fa6eb9311f54d46ee32021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf3a867d4e16e0849e1f32babd729e8f8955984f2075b0d34e0befd9b9407861 0.600000000000 1701062 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": 1214285, "vin": [ { "gen": { "height": 1214275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf3a867d4e16e0849e1f32babd729e8f8955984f2075b0d34e0befd9b9407861" } } ], "extra": [ 1, 11, 242, 54, 252, 87, 83, 240, 245, 250, 137, 93, 192, 83, 56, 59, 235, 9, 3, 33, 225, 252, 148, 15, 166, 235, 147, 17, 245, 77, 70, 238, 50, 2, 17, 0, 0, 0, 4, 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