Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4bf60168f258205622b74b34ff938bb4c907715b6ca0aa5f128fb6f89b34c0

Tx prefix hash: f515f265f0ae378fcb5105966d8b09c5cf4c6d12d7e35c7e3cdacd8e508240ea
Tx public key: 9436a3b369d898181ab172592517aadc86748d4a738276bdff416037d0ee1ce4
Timestamp: 1657079368 Timestamp [UCT]: 2022-07-06 03:49:28 Age [y:d:h:m:s]: 02:257:17:44:11
Block: 537609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705366 RingCT/type: yes/0
Extra: 019436a3b369d898181ab172592517aadc86748d4a738276bdff416037d0ee1ce4021100000001faf35c9c000000000000000000

1 output(s) for total of 10.154963373000 dcy

stealth address amount amount idx
00: 32ca2ab014ac0afe4ae7e014d65dbb449597251cf979c1a16a66ba563ad2f0ce 10.154963373000 967514 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": 537619, "vin": [ { "gen": { "height": 537609 } } ], "vout": [ { "amount": 10154963373, "target": { "key": "32ca2ab014ac0afe4ae7e014d65dbb449597251cf979c1a16a66ba563ad2f0ce" } } ], "extra": [ 1, 148, 54, 163, 179, 105, 216, 152, 24, 26, 177, 114, 89, 37, 23, 170, 220, 134, 116, 141, 74, 115, 130, 118, 189, 255, 65, 96, 55, 208, 238, 28, 228, 2, 17, 0, 0, 0, 1, 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