Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60278e500afd25484c19d77db1e08646e11cb0b595ff15fd434f4388940134cc

Tx prefix hash: 8c217ff1c6909d5e6f5e182213d9981f75ef577c4bca97b5b7e4342f4d725dbc
Tx public key: bb28d7b523b3d341b8c4b4c4984d64939fc1cdd260d6b7aac39264b626132eed
Timestamp: 1614056818 Timestamp [UCT]: 2021-02-23 05:06:58 Age [y:d:h:m:s]: 03:305:08:57:54
Block: 204742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977468 RingCT/type: yes/0
Extra: 01bb28d7b523b3d341b8c4b4c4984d64939fc1cdd260d6b7aac39264b626132eed0211000002f04ea414e5000000000000000000

1 output(s) for total of 128.707951370000 dcy

stealth address amount amount idx
00: bf2b2cd7c14f756aa8bcacd8e2e89c039193e9ffcbbbcaa4d3fe07030e64cc4f 128.707951370000 418414 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": 204752, "vin": [ { "gen": { "height": 204742 } } ], "vout": [ { "amount": 128707951370, "target": { "key": "bf2b2cd7c14f756aa8bcacd8e2e89c039193e9ffcbbbcaa4d3fe07030e64cc4f" } } ], "extra": [ 1, 187, 40, 215, 181, 35, 179, 211, 65, 184, 196, 180, 196, 152, 77, 100, 147, 159, 193, 205, 210, 96, 214, 183, 170, 195, 146, 100, 182, 38, 19, 46, 237, 2, 17, 0, 0, 2, 240, 78, 164, 20, 229, 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