Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52135155bf71cc7b2c82347044baf6b38267dd94b95293b87e65f1c292a9b885

Tx prefix hash: 1a36cfb5fad050fdf2c4af69429ccffa7f3703b6439d5adeefd4521bae79c2df
Tx public key: 8671317e27a932f98b599d3571de6c8c73f6fae6054ddd2e4505967a12739eeb
Timestamp: 1677465105 Timestamp [UCT]: 2023-02-27 02:31:45 Age [y:d:h:m:s]: 02:051:05:20:57
Block: 705804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558199 RingCT/type: yes/0
Extra: 018671317e27a932f98b599d3571de6c8c73f6fae6054ddd2e4505967a12739eeb02110000000183600029000000000000000000

1 output(s) for total of 2.814350992000 dcy

stealth address amount amount idx
00: 5767b13ea65ba97a8947bc3f3a7cbc268a1570d8f9168435d58c99160ba6cd3c 2.814350992000 1149517 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": 705814, "vin": [ { "gen": { "height": 705804 } } ], "vout": [ { "amount": 2814350992, "target": { "key": "5767b13ea65ba97a8947bc3f3a7cbc268a1570d8f9168435d58c99160ba6cd3c" } } ], "extra": [ 1, 134, 113, 49, 126, 39, 169, 50, 249, 139, 89, 157, 53, 113, 222, 108, 140, 115, 246, 250, 230, 5, 77, 221, 46, 69, 5, 150, 122, 18, 115, 158, 235, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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