Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af056520098c011746bb2a810b9242524e5ba7b8130b71d46e34b7efe71bef74

Tx prefix hash: 384d1389260d7165c94d08bba9e97d721b93cabb7b275d17dcc1d33a7a1282d4
Tx public key: c496635f5c85cf8aa0df98347147ad60486f2fa4c387f9d6a406b42253ea67ab
Timestamp: 1721226815 Timestamp [UCT]: 2024-07-17 14:33:35 Age [y:d:h:m:s]: 00:220:23:27:49
Block: 1067743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157796 RingCT/type: yes/0
Extra: 01c496635f5c85cf8aa0df98347147ad60486f2fa4c387f9d6a406b42253ea67ab02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f9f0d992d97c193cc4047bc8caf33f3b2f3ec2a97f80a384b2765055db36328 0.600000000000 1538638 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": 1067753, "vin": [ { "gen": { "height": 1067743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f9f0d992d97c193cc4047bc8caf33f3b2f3ec2a97f80a384b2765055db36328" } } ], "extra": [ 1, 196, 150, 99, 95, 92, 133, 207, 138, 160, 223, 152, 52, 113, 71, 173, 96, 72, 111, 47, 164, 195, 135, 249, 214, 164, 6, 180, 34, 83, 234, 103, 171, 2, 17, 0, 0, 0, 4, 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