Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14ce60beeaf2027ac73c636d85aade65edf4b53640ea57c8fb47009b99a3f1a4

Tx prefix hash: 2897d65600f4c6e50d8c04c260843e10a6e03c031da44312c0a7857a79aec770
Tx public key: 47667e2d5d041c1f8abd82271a744d6a876a1c820266385c93e4342351a101f1
Timestamp: 1684694623 Timestamp [UCT]: 2023-05-21 18:43:43 Age [y:d:h:m:s]: 01:331:11:20:50
Block: 765115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498118 RingCT/type: yes/0
Extra: 0147667e2d5d041c1f8abd82271a744d6a876a1c820266385c93e4342351a101f102110000000575e3f0e9000000000000000000

1 output(s) for total of 1.790014593000 dcy

stealth address amount amount idx
00: 84202cb59411ae38dfd7e95de6c91215ce447fa29d7542f9f587bf803fc94157 1.790014593000 1214086 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": 765125, "vin": [ { "gen": { "height": 765115 } } ], "vout": [ { "amount": 1790014593, "target": { "key": "84202cb59411ae38dfd7e95de6c91215ce447fa29d7542f9f587bf803fc94157" } } ], "extra": [ 1, 71, 102, 126, 45, 93, 4, 28, 31, 138, 189, 130, 39, 26, 116, 77, 106, 135, 106, 28, 130, 2, 102, 56, 92, 147, 228, 52, 35, 81, 161, 1, 241, 2, 17, 0, 0, 0, 5, 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