Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4594fb0ec38b4c8a29c66ca1cefe645c4d679d2cc0ae070b8c74e8f86e39d6b

Tx prefix hash: 80036878ae86351f71a7fab8a61ffb679e2dbb1c32e301df1f0b6d7d7fcc6c0f
Tx public key: 734ddd1bb96d3ecf8f4ebb9b89eb3bf95afa65b33a1776b7f5a78648e3da6545
Timestamp: 1648642849 Timestamp [UCT]: 2022-03-30 12:20:49 Age [y:d:h:m:s]: 02:273:22:33:10
Block: 469578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715384 RingCT/type: yes/0
Extra: 01734ddd1bb96d3ecf8f4ebb9b89eb3bf95afa65b33a1776b7f5a78648e3da6545021100000008bf7ee4e7000000000000000000

1 output(s) for total of 17.064493606000 dcy

stealth address amount amount idx
00: 22e3634f7ef32f227c1426cdf259d54d0650983b29cc28c9dccbb5ec099f6ed9 17.064493606000 888546 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": 469588, "vin": [ { "gen": { "height": 469578 } } ], "vout": [ { "amount": 17064493606, "target": { "key": "22e3634f7ef32f227c1426cdf259d54d0650983b29cc28c9dccbb5ec099f6ed9" } } ], "extra": [ 1, 115, 77, 221, 27, 185, 109, 62, 207, 143, 78, 187, 155, 137, 235, 59, 249, 90, 250, 101, 179, 58, 23, 118, 183, 245, 167, 134, 72, 227, 218, 101, 69, 2, 17, 0, 0, 0, 8, 191, 126, 228, 231, 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