Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6c1c3874fd81ea39708be5efe7b1dc310261e06f5054b95cf37801b41cf50bb

Tx prefix hash: a1678f153cf2e991833103fc17ab65ee4d177fc74de82ea86714c115793ef752
Tx public key: b1e18e976c8cf3e72376c50fa4b7bd1305bca0ce49c866e650d9d7fe1ef9d36b
Timestamp: 1710155382 Timestamp [UCT]: 2024-03-11 11:09:42 Age [y:d:h:m:s]: 00:258:02:49:18
Block: 975954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184780 RingCT/type: yes/0
Extra: 01b1e18e976c8cf3e72376c50fa4b7bd1305bca0ce49c866e650d9d7fe1ef9d36b02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e5d3730250b7519cc239164e83937ff977e54c7c6408a41d4a8d79884094d6a 0.600000000000 1435933 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": 975964, "vin": [ { "gen": { "height": 975954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e5d3730250b7519cc239164e83937ff977e54c7c6408a41d4a8d79884094d6a" } } ], "extra": [ 1, 177, 225, 142, 151, 108, 140, 243, 231, 35, 118, 197, 15, 164, 183, 189, 19, 5, 188, 160, 206, 73, 200, 102, 230, 80, 217, 215, 254, 30, 249, 211, 107, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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