Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5731fa8b0329eec6fd5c79c0a52e485c53a19e82176a52942a69e9418a7d7c9

Tx prefix hash: dee2a52b2e23a07f45fbbdab40418687a41840e3e21c157d3473e44c47e0359e
Tx public key: e94551dc15f7b8fee5eff45a476afa61f7a2aea822be0d290c371386d5cb7e33
Timestamp: 1714021771 Timestamp [UCT]: 2024-04-25 05:09:31 Age [y:d:h:m:s]: 00:213:23:39:20
Block: 1007984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153177 RingCT/type: yes/0
Extra: 01e94551dc15f7b8fee5eff45a476afa61f7a2aea822be0d290c371386d5cb7e3302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0237055433e4ad0f6b26d6f1867be69cbc849a7b8967dcf32188f59778962e46 0.600000000000 1469450 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": 1007994, "vin": [ { "gen": { "height": 1007984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0237055433e4ad0f6b26d6f1867be69cbc849a7b8967dcf32188f59778962e46" } } ], "extra": [ 1, 233, 69, 81, 220, 21, 247, 184, 254, 229, 239, 244, 90, 71, 106, 250, 97, 247, 162, 174, 168, 34, 190, 13, 41, 12, 55, 19, 134, 213, 203, 126, 51, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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