Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be60390f0c44df9814d724cff779a384039f4ee063bd0ac6c1d1593435e4a12

Tx prefix hash: fcb0d95420dd00e1a18ea7ad216d51d6691db10bfe0f39d5e959d43308671e16
Tx public key: c0c5da0cea42bb2c80a593f8f618d1c5c09f232e0a51045a2ba7a155e6e70069
Timestamp: 1712406974 Timestamp [UCT]: 2024-04-06 12:36:14 Age [y:d:h:m:s]: 01:213:13:14:39
Block: 994580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411301 RingCT/type: yes/0
Extra: 01c0c5da0cea42bb2c80a593f8f618d1c5c09f232e0a51045a2ba7a155e6e700690211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaedf6f411b8c70c9b80494019efc3bda503d44034f4d26a8cd58350fa02560a 0.600000000000 1454984 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": 994590, "vin": [ { "gen": { "height": 994580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaedf6f411b8c70c9b80494019efc3bda503d44034f4d26a8cd58350fa02560a" } } ], "extra": [ 1, 192, 197, 218, 12, 234, 66, 187, 44, 128, 165, 147, 248, 246, 24, 209, 197, 192, 159, 35, 46, 10, 81, 4, 90, 43, 167, 161, 85, 230, 231, 0, 105, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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