Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286d04e89c39822b539c1f483406bc84fd1f58a0a5a249fced9ebcb724f4fbee

Tx prefix hash: 5cb257ba6f1352eab0d94057f0e47441f2947fcf64b0b1b5e5e4d1045fbb3111
Tx public key: 113ff88460caf6203584f7bb1ed9a06d84916671f5d8cf692dd7e53fcb055631
Timestamp: 1726577514 Timestamp [UCT]: 2024-09-17 12:51:54 Age [y:d:h:m:s]: 00:225:17:22:43
Block: 1112090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161150 RingCT/type: yes/0
Extra: 01113ff88460caf6203584f7bb1ed9a06d84916671f5d8cf692dd7e53fcb05563102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da9125c1ed87d05fd3f1c79e54bca56bc88848fbbe50b42fd56b5a85cdcc399 0.600000000000 1591287 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": 1112100, "vin": [ { "gen": { "height": 1112090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da9125c1ed87d05fd3f1c79e54bca56bc88848fbbe50b42fd56b5a85cdcc399" } } ], "extra": [ 1, 17, 63, 248, 132, 96, 202, 246, 32, 53, 132, 247, 187, 30, 217, 160, 109, 132, 145, 102, 113, 245, 216, 207, 105, 45, 215, 229, 63, 203, 5, 86, 49, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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