Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0f9f79d70406e53a8f9ea8d41d677cdf83556c37269cc7fa4abd5585c67929

Tx prefix hash: b7a51dca4a26a1fe0408073cad411c96c3890eceefc94f793c67b0aa61f45453
Tx public key: 3ac080fd34f0e429f541d344d5bbbe5a7956e864c78fc3ffc45421ce49d48447
Timestamp: 1711941457 Timestamp [UCT]: 2024-04-01 03:17:37 Age [y:d:h:m:s]: 01:002:16:49:46
Block: 990740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262885 RingCT/type: yes/0
Extra: 013ac080fd34f0e429f541d344d5bbbe5a7956e864c78fc3ffc45421ce49d4844702110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa7ab75a6ae70af23e2e8944b0d144d35c7f8ebdf09d36d79ac3102dcb13410 0.600000000000 1451068 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": 990750, "vin": [ { "gen": { "height": 990740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa7ab75a6ae70af23e2e8944b0d144d35c7f8ebdf09d36d79ac3102dcb13410" } } ], "extra": [ 1, 58, 192, 128, 253, 52, 240, 228, 41, 245, 65, 211, 68, 213, 187, 190, 90, 121, 86, 232, 100, 199, 143, 195, 255, 196, 84, 33, 206, 73, 212, 132, 71, 2, 17, 0, 0, 0, 7, 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