Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91b90cd872e36723eb6d64b3aa061bb2adc0a4e19fb9ceac0d4d0d3288d24a2

Tx prefix hash: 5ccc320e929033369d68fb2f4aa2f74a0f3a80918d91d3e54853b35db4ba5349
Tx public key: 12c1fc0319946c3a6a1cc530b211897ba8fec5306ccd8b381f5b0be6f6f2aec1
Timestamp: 1722063427 Timestamp [UCT]: 2024-07-27 06:57:07 Age [y:d:h:m:s]: 00:247:10:22:38
Block: 1074655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176752 RingCT/type: yes/0
Extra: 0112c1fc0319946c3a6a1cc530b211897ba8fec5306ccd8b381f5b0be6f6f2aec102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb93e564b2d082dd4a5866cd6bfc10437199cf0a6bb866efab0d2d88c5e1629a 0.600000000000 1547172 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": 1074665, "vin": [ { "gen": { "height": 1074655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb93e564b2d082dd4a5866cd6bfc10437199cf0a6bb866efab0d2d88c5e1629a" } } ], "extra": [ 1, 18, 193, 252, 3, 25, 148, 108, 58, 106, 28, 197, 48, 178, 17, 137, 123, 168, 254, 197, 48, 108, 205, 139, 56, 31, 91, 11, 230, 246, 242, 174, 193, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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