Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc798a547820b3450e979180f76891b4d2fc1e24ff5604e8e264cc757bb93100

Tx prefix hash: bb9e157e17239eedca506ac4a54149913c0b07542b46e489631630d7d5db11da
Tx public key: fe8e90ed7c74a963ccabce0ba3d83b24f83469f37ddf0aa4927eb31afc20d31a
Timestamp: 1699713074 Timestamp [UCT]: 2023-11-11 14:31:14 Age [y:d:h:m:s]: 01:130:13:06:06
Block: 889362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354505 RingCT/type: yes/0
Extra: 01fe8e90ed7c74a963ccabce0ba3d83b24f83469f37ddf0aa4927eb31afc20d31a021100000002faf35c9c000000000000000000

1 output(s) for total of 0.693704483000 dcy

stealth address amount amount idx
00: 0cb9c5bb328295cc642255cf6b8c25a8354c83b7532a68f3d5cc4e7b0d504752 0.693704483000 1345357 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": 889372, "vin": [ { "gen": { "height": 889362 } } ], "vout": [ { "amount": 693704483, "target": { "key": "0cb9c5bb328295cc642255cf6b8c25a8354c83b7532a68f3d5cc4e7b0d504752" } } ], "extra": [ 1, 254, 142, 144, 237, 124, 116, 169, 99, 204, 171, 206, 11, 163, 216, 59, 36, 248, 52, 105, 243, 125, 223, 10, 164, 146, 126, 179, 26, 252, 32, 211, 26, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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