Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ddd50bc05c58314a2685c1d2b7ef5b2b5c1cfffd5e43943b350354568343ab

Tx prefix hash: 07d6cd2a4c20c01ef60d36c54386fbd4c89355d852c05f20f10270e6d5f3d3f2
Tx public key: c80e3b69f83512faafdc7ff121dbb02739e8d50d38df5bf43493c62e1a15d988
Timestamp: 1736796725 Timestamp [UCT]: 2025-01-13 19:32:05 Age [y:d:h:m:s]: 00:155:18:44:50
Block: 1196663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111033 RingCT/type: yes/0
Extra: 01c80e3b69f83512faafdc7ff121dbb02739e8d50d38df5bf43493c62e1a15d9880211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79595709ea40e949e3191fe331d45c889783cac32eb8926ceae95a44df2dfd2 0.600000000000 1683264 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": 1196673, "vin": [ { "gen": { "height": 1196663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79595709ea40e949e3191fe331d45c889783cac32eb8926ceae95a44df2dfd2" } } ], "extra": [ 1, 200, 14, 59, 105, 248, 53, 18, 250, 175, 220, 127, 241, 33, 219, 176, 39, 57, 232, 213, 13, 56, 223, 91, 244, 52, 147, 198, 46, 26, 21, 217, 136, 2, 17, 0, 0, 0, 2, 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