Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 394c6504f75f6aff55a6bcbd6613e1c4695b43479ad1c2f5c07cc5d2f4acd938

Tx prefix hash: 9087daa8026e6c97d95c908771cdd6dbe6a2f3eda8d4ddb410de528e47d0f784
Tx public key: 5d1a0a63d1f3cb3454b987457487b7c4d649749f0c0eae6488a0ae129c436345
Timestamp: 1714929395 Timestamp [UCT]: 2024-05-05 17:16:35 Age [y:d:h:m:s]: 00:210:08:59:01
Block: 1015523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150589 RingCT/type: yes/0
Extra: 015d1a0a63d1f3cb3454b987457487b7c4d649749f0c0eae6488a0ae129c4363450211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 685445e8eecdfe7f4a7538d84a5f84e8dc0be123f1f087d1d958c2ac4bc1fb42 0.600000000000 1478914 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": 1015533, "vin": [ { "gen": { "height": 1015523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "685445e8eecdfe7f4a7538d84a5f84e8dc0be123f1f087d1d958c2ac4bc1fb42" } } ], "extra": [ 1, 93, 26, 10, 99, 209, 243, 203, 52, 84, 185, 135, 69, 116, 135, 183, 196, 214, 73, 116, 159, 12, 14, 174, 100, 136, 160, 174, 18, 156, 67, 99, 69, 2, 17, 0, 0, 0, 4, 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