Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afff4bc9e762be0d76c9b4a1a4093e265617fc23e3de2a0bf3014f609c6e76fc

Tx prefix hash: b3e8dc9be8e26a7a05511fe3fb82e47771a9a9b1918cbe773dd68efec6578ee3
Tx public key: e9f4b1e380a1bedfd6219cd97c9002f7dc40fed8b189038b0ac347917f112777
Timestamp: 1723952530 Timestamp [UCT]: 2024-08-18 03:42:10 Age [y:d:h:m:s]: 00:226:23:19:54
Block: 1090326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162070 RingCT/type: yes/0
Extra: 01e9f4b1e380a1bedfd6219cd97c9002f7dc40fed8b189038b0ac347917f11277702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29eddc3e691494e770473bf3d62ff8d2fee5aa63589bec87189654a3d18d399 0.600000000000 1564949 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": 1090336, "vin": [ { "gen": { "height": 1090326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29eddc3e691494e770473bf3d62ff8d2fee5aa63589bec87189654a3d18d399" } } ], "extra": [ 1, 233, 244, 177, 227, 128, 161, 190, 223, 214, 33, 156, 217, 124, 144, 2, 247, 220, 64, 254, 216, 177, 137, 3, 139, 10, 195, 71, 145, 127, 17, 39, 119, 2, 17, 0, 0, 0, 10, 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