Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5c9601df40f6176a4bbf42ddb2da8a211df304fbfe9ecb505da4ebb79b59c7

Tx prefix hash: 96aaefc3dbc2c8079e3ec249dae04896cf1d717a97e3a8ab1277504bcee2e670
Tx public key: ce26bb20d3e82d538e216a0ffdeda8502ca77549f11dc802b34f41841ed9924a
Timestamp: 1672846714 Timestamp [UCT]: 2023-01-04 15:38:34 Age [y:d:h:m:s]: 02:121:18:35:32
Block: 667501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608723 RingCT/type: yes/0
Extra: 01ce26bb20d3e82d538e216a0ffdeda8502ca77549f11dc802b34f41841ed9924a02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.770792106000 dcy

stealth address amount amount idx
00: 65c34b94e2960e30baeb587b4215625211387df05ee3867690318831104c4e2d 3.770792106000 1108702 of 0

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": 667511, "vin": [ { "gen": { "height": 667501 } } ], "vout": [ { "amount": 3770792106, "target": { "key": "65c34b94e2960e30baeb587b4215625211387df05ee3867690318831104c4e2d" } } ], "extra": [ 1, 206, 38, 187, 32, 211, 232, 45, 83, 142, 33, 106, 15, 253, 237, 168, 80, 44, 167, 117, 73, 241, 29, 200, 2, 179, 79, 65, 132, 30, 217, 146, 74, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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