Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc30842bad3d9315eb18a2eaad2fd05ab2c0cb3fa71ee46e3c06a88e14f3da5

Tx prefix hash: e053b9f9eb040037e68ce0dff280fdb111b15f84d5a32cfeacbfbcc411a7dee2
Tx public key: f3e25a48a3185ca30ab2e9b7840c3dc56fe7aaab35134244a4fc8c91b2314058
Timestamp: 1711190046 Timestamp [UCT]: 2024-03-23 10:34:06 Age [y:d:h:m:s]: 00:293:09:37:11
Block: 984540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210000 RingCT/type: yes/0
Extra: 01f3e25a48a3185ca30ab2e9b7840c3dc56fe7aaab35134244a4fc8c91b231405802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a53d6c2f499bd62104cafe6b5ac99e3f0d14f5e462c97f536dab948ad655833 0.600000000000 1444711 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": 984550, "vin": [ { "gen": { "height": 984540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a53d6c2f499bd62104cafe6b5ac99e3f0d14f5e462c97f536dab948ad655833" } } ], "extra": [ 1, 243, 226, 90, 72, 163, 24, 92, 163, 10, 178, 233, 183, 132, 12, 61, 197, 111, 231, 170, 171, 53, 19, 66, 68, 164, 252, 140, 145, 178, 49, 64, 88, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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