Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa275eab77a2e67882fbefa5a5c694d9d89151a7bca47667e181d8b7fdea6d07

Tx prefix hash: a416929b20f8aeb35590b838d926fac6141b53cf74fb5b017085a87197b1d999
Tx public key: 4154a1e39f1816f9c3a9eaf84fb3384dbb3ba689e53285d160b3429ecb4c45e8
Timestamp: 1577605262 Timestamp [UCT]: 2019-12-29 07:41:02 Age [y:d:h:m:s]: 05:360:16:34:07
Block: 34160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1405339 RingCT/type: yes/0
Extra: 014154a1e39f1816f9c3a9eaf84fb3384dbb3ba689e53285d160b3429ecb4c45e80211000000044943cd9f000000000000000000

1 output(s) for total of 472.949309456000 dcy

stealth address amount amount idx
00: caf4d411ea05c3d98d8ed47f0ac9ae7fbb55148269f188019624c8b55a8ffab8 472.949309456000 57500 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": 34170, "vin": [ { "gen": { "height": 34160 } } ], "vout": [ { "amount": 472949309456, "target": { "key": "caf4d411ea05c3d98d8ed47f0ac9ae7fbb55148269f188019624c8b55a8ffab8" } } ], "extra": [ 1, 65, 84, 161, 227, 159, 24, 22, 249, 195, 169, 234, 248, 79, 179, 56, 77, 187, 59, 166, 137, 229, 50, 133, 209, 96, 179, 66, 158, 203, 76, 69, 232, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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