Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864901854c858ce46da34c7d25eb87f0f7b74a5023dd2bfb8c61680d25a3dbeb

Tx prefix hash: e4dd80dfc546aeff87f0bf715211ff512b91da670a5ef412f90b942bd6f4d763
Tx public key: ddb8b47ae3324bbe8e1b6db80a335706cca6236c7781feb08604fbee8c8363ae
Timestamp: 1735670174 Timestamp [UCT]: 2024-12-31 18:36:14 Age [y:d:h:m:s]: 00:102:09:08:00
Block: 1187335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72961 RingCT/type: yes/0
Extra: 01ddb8b47ae3324bbe8e1b6db80a335706cca6236c7781feb08604fbee8c8363ae0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39e787c86c2f4941e05704aef3520fd121d56324b2f33b6b7f6f9f0c86bd728f 0.600000000000 1673824 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": 1187345, "vin": [ { "gen": { "height": 1187335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39e787c86c2f4941e05704aef3520fd121d56324b2f33b6b7f6f9f0c86bd728f" } } ], "extra": [ 1, 221, 184, 180, 122, 227, 50, 75, 190, 142, 27, 109, 184, 10, 51, 87, 6, 204, 166, 35, 108, 119, 129, 254, 176, 134, 4, 251, 238, 140, 131, 99, 174, 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