Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91c404f6cd8d75cd93f90de0bc38f6d0e1e516f8dd2e2a9edff21af5e8fc80d1

Tx prefix hash: 2c5dc85d91b409ebcd8ec99920ddac5f8a2aa23e6b8902e7e87038678a2efa7b
Tx public key: 11976684b7cdaaf1a3cafa4f9a4251427d2e8332a8092576ab0f9e612ca1d04d
Timestamp: 1698208311 Timestamp [UCT]: 2023-10-25 04:31:51 Age [y:d:h:m:s]: 01:089:20:41:08
Block: 877110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325404 RingCT/type: yes/0
Extra: 0111976684b7cdaaf1a3cafa4f9a4251427d2e8332a8092576ab0f9e612ca1d04d02110000000833af99f4000000000000000000

1 output(s) for total of 0.761676368000 dcy

stealth address amount amount idx
00: 6040c8e575fa6d3c7f23565748fdc05833fe300fc93c99d2dd45c338444d58d9 0.761676368000 1332470 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": 877120, "vin": [ { "gen": { "height": 877110 } } ], "vout": [ { "amount": 761676368, "target": { "key": "6040c8e575fa6d3c7f23565748fdc05833fe300fc93c99d2dd45c338444d58d9" } } ], "extra": [ 1, 17, 151, 102, 132, 183, 205, 170, 241, 163, 202, 250, 79, 154, 66, 81, 66, 125, 46, 131, 50, 168, 9, 37, 118, 171, 15, 158, 97, 44, 161, 208, 77, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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