Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68edcd83fee99c66c63417ca9ca48ccc0b37f1f1c52ceb48d8034b8990643a8

Tx prefix hash: 0ae47d3fe1c0f15cf701138729604266533e7b9e99cc903e8276df6ceec71dd7
Tx public key: 9b24fdd108f4f2b0dc930865e8bfdc95b983b3e6d26ab721c0a09e44d07b1c0f
Timestamp: 1705481961 Timestamp [UCT]: 2024-01-17 08:59:21 Age [y:d:h:m:s]: 01:104:14:16:48
Block: 937176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335863 RingCT/type: yes/0
Extra: 019b24fdd108f4f2b0dc930865e8bfdc95b983b3e6d26ab721c0a09e44d07b1c0f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d02087e1d2abb29ad3ea6bd7f655d6a89e6de0d014e929802602f23f4b0dfeb3 0.600000000000 1395220 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": 937186, "vin": [ { "gen": { "height": 937176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d02087e1d2abb29ad3ea6bd7f655d6a89e6de0d014e929802602f23f4b0dfeb3" } } ], "extra": [ 1, 155, 36, 253, 209, 8, 244, 242, 176, 220, 147, 8, 101, 232, 191, 220, 149, 185, 131, 179, 230, 210, 106, 183, 33, 192, 160, 158, 68, 208, 123, 28, 15, 2, 17, 0, 0, 0, 2, 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