Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595cd45b4ef1a6eb4daa47bd0c54adb8cd783b23be49feb7c4137c64079b304c

Tx prefix hash: fd95ef270b4919b60f01679e66d6e74c8f37e76058bf0379a6bcd33e27661340
Tx public key: dcef010add7129f3a3a62177caaeafdc7d65cfca6d3949f9f10e26f4f09b1ab3
Timestamp: 1722320420 Timestamp [UCT]: 2024-07-30 06:20:20 Age [y:d:h:m:s]: 00:296:06:28:53
Block: 1076795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211678 RingCT/type: yes/0
Extra: 01dcef010add7129f3a3a62177caaeafdc7d65cfca6d3949f9f10e26f4f09b1ab302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f3311e35ee09219e9073dc2732b84e83cbdf4c52e2207ace10b2ec36493dd83 0.600000000000 1549336 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": 1076805, "vin": [ { "gen": { "height": 1076795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f3311e35ee09219e9073dc2732b84e83cbdf4c52e2207ace10b2ec36493dd83" } } ], "extra": [ 1, 220, 239, 1, 10, 221, 113, 41, 243, 163, 166, 33, 119, 202, 174, 175, 220, 125, 101, 207, 202, 109, 57, 73, 249, 241, 14, 38, 244, 240, 155, 26, 179, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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