Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 656f6fee64a97359367d14a4486a151d7e5df6859e8c86b188fe9449129a8b0a

Tx prefix hash: fdd962bebbde2ef0137af241b39616f5d8f10406a50b736d45872a991bb0351a
Tx public key: 901eac8e5c852e3b5bbf1de51691b8a09601f4a8da79eb020a5a59233d3451ed
Timestamp: 1735024779 Timestamp [UCT]: 2024-12-24 07:19:39 Age [y:d:h:m:s]: 00:331:23:46:35
Block: 1182009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234769 RingCT/type: yes/0
Extra: 01901eac8e5c852e3b5bbf1de51691b8a09601f4a8da79eb020a5a59233d3451ed0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df119171766512342af2a2831e55cc41cc08093bc9f860e24abf2a3d90a84185 0.600000000000 1668438 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": 1182019, "vin": [ { "gen": { "height": 1182009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df119171766512342af2a2831e55cc41cc08093bc9f860e24abf2a3d90a84185" } } ], "extra": [ 1, 144, 30, 172, 142, 92, 133, 46, 59, 91, 191, 29, 229, 22, 145, 184, 160, 150, 1, 244, 168, 218, 121, 235, 2, 10, 90, 89, 35, 61, 52, 81, 237, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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