Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cb380aef791294173de4ef4d3d6093ea0e7a1266cae3119d2c32dbf0612553d

Tx prefix hash: 50209c8f8d7a18fbd976bde57ece2e5216521ad353e004abf2fcc47223a8881d
Tx public key: 9a5b98ebb0f1ed6df3c687f7d37c628f1df14475e96627ed5549ea5383e3a70f
Timestamp: 1700760593 Timestamp [UCT]: 2023-11-23 17:29:53 Age [y:d:h:m:s]: 01:069:17:16:52
Block: 898053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310968 RingCT/type: yes/0
Extra: 019a5b98ebb0f1ed6df3c687f7d37c628f1df14475e96627ed5549ea5383e3a70f0211000000044b8f5122000000000000000000

1 output(s) for total of 0.649198635000 dcy

stealth address amount amount idx
00: b3f8f6fd25f2c7a2dab0be5f934f5bf4795b94bfbda9f662e3d631d43ca524b8 0.649198635000 1354456 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": 898063, "vin": [ { "gen": { "height": 898053 } } ], "vout": [ { "amount": 649198635, "target": { "key": "b3f8f6fd25f2c7a2dab0be5f934f5bf4795b94bfbda9f662e3d631d43ca524b8" } } ], "extra": [ 1, 154, 91, 152, 235, 176, 241, 237, 109, 243, 198, 135, 247, 211, 124, 98, 143, 29, 241, 68, 117, 233, 102, 39, 237, 85, 73, 234, 83, 131, 227, 167, 15, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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