Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e85591c90d4fb4ece2a44de8b18263fa17c25cad0e0e919f8044ad3a44518437

Tx prefix hash: 66cfd263a1f2a229c0ce7c20abd5ea93117cc14fe50311aa3c4f41cb642d7671
Tx public key: bdec993da27a4faa8d6fdc7c1c34422e8e778d3c06f89a1579983afae1271cf9
Timestamp: 1698516634 Timestamp [UCT]: 2023-10-28 18:10:34 Age [y:d:h:m:s]: 02:037:05:55:01
Block: 879664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546232 RingCT/type: yes/0
Extra: 01bdec993da27a4faa8d6fdc7c1c34422e8e778d3c06f89a1579983afae1271cf902110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.746978351000 dcy

stealth address amount amount idx
00: f05529b706e6b2c5142dc5848f3689bb6d5eecb770a3f2e245e5bb27043514a3 0.746978351000 1335198 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": 879674, "vin": [ { "gen": { "height": 879664 } } ], "vout": [ { "amount": 746978351, "target": { "key": "f05529b706e6b2c5142dc5848f3689bb6d5eecb770a3f2e245e5bb27043514a3" } } ], "extra": [ 1, 189, 236, 153, 61, 162, 122, 79, 170, 141, 111, 220, 124, 28, 52, 66, 46, 142, 119, 141, 60, 6, 248, 154, 21, 121, 152, 58, 250, 225, 39, 28, 249, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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