Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7749ccc513e55a73fc62e81d853153b6dd98d08498995d1af174fe57459182e

Tx prefix hash: 31f17df82f923ec01c40fbd52b66c6c947130a98daaf2bfb1b376f76cf0edaec
Tx public key: b5ea82bc11bd4a3f37c21e33dce58d25eff6425740e91430a5d2af2d8daf5b69
Timestamp: 1671864602 Timestamp [UCT]: 2022-12-24 06:50:02 Age [y:d:h:m:s]: 02:091:08:16:43
Block: 659372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586965 RingCT/type: yes/0
Extra: 01b5ea82bc11bd4a3f37c21e33dce58d25eff6425740e91430a5d2af2d8daf5b6902110000000133af99f4000000000000000000

1 output(s) for total of 4.010761325000 dcy

stealth address amount amount idx
00: ad723be29ce55f88ff191e7400edeed9f50fdf11120d1dc72b592aa1ba44bb44 4.010761325000 1100073 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": 659382, "vin": [ { "gen": { "height": 659372 } } ], "vout": [ { "amount": 4010761325, "target": { "key": "ad723be29ce55f88ff191e7400edeed9f50fdf11120d1dc72b592aa1ba44bb44" } } ], "extra": [ 1, 181, 234, 130, 188, 17, 189, 74, 63, 55, 194, 30, 51, 220, 229, 141, 37, 239, 246, 66, 87, 64, 233, 20, 48, 165, 210, 175, 45, 141, 175, 91, 105, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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