Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649335041f34005634e91b969c8ebe1c9bb49bcaef7d1538274d8765423f85df

Tx prefix hash: 501761851efc2e72c2411b273c068cb79e365e3304b52d2c788972b910f4ea18
Tx public key: 94722fe4e8e2b21a545ad508ef68e35e125aebef9426b3052cc86a0dd58b3d31
Timestamp: 1696885976 Timestamp [UCT]: 2023-10-09 21:12:56 Age [y:d:h:m:s]: 01:141:21:49:26
Block: 866134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362423 RingCT/type: yes/0
Extra: 0194722fe4e8e2b21a545ad508ef68e35e125aebef9426b3052cc86a0dd58b3d3102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.828206323000 dcy

stealth address amount amount idx
00: 22f471131a6d6a0ee3bf69e62ba2484a9e8782c3954d5a523c6d220106ec69d7 0.828206323000 1320706 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": 866144, "vin": [ { "gen": { "height": 866134 } } ], "vout": [ { "amount": 828206323, "target": { "key": "22f471131a6d6a0ee3bf69e62ba2484a9e8782c3954d5a523c6d220106ec69d7" } } ], "extra": [ 1, 148, 114, 47, 228, 232, 226, 178, 26, 84, 90, 213, 8, 239, 104, 227, 94, 18, 90, 235, 239, 148, 38, 179, 5, 44, 200, 106, 13, 213, 139, 61, 49, 2, 17, 0, 0, 0, 1, 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