Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64a74a4d51b875e134b3bd3d79b5d9d61a830caca5ef22c9291307eadb3e012

Tx prefix hash: 063c341b15ba782d4a36dd09ab7487d27dd84c752b3ca78264c89254a4697ade
Tx public key: c2db0f9c6575bf3c33672c9c17d55a0849f89d6ab12a770fdb56d91ebd4025df
Timestamp: 1625402951 Timestamp [UCT]: 2021-07-04 12:49:11 Age [y:d:h:m:s]: 03:138:23:18:56
Block: 288146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 868956 RingCT/type: yes/0
Extra: 01c2db0f9c6575bf3c33672c9c17d55a0849f89d6ab12a770fdb56d91ebd4025df021100000007694a138f000000000000000000

1 output(s) for total of 68.116636437000 dcy

stealth address amount amount idx
00: 447b9a2c0c8d628169f23af6974f2b90ea013fda2144c275ab12183a9c43c4c2 68.116636437000 603733 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": 288156, "vin": [ { "gen": { "height": 288146 } } ], "vout": [ { "amount": 68116636437, "target": { "key": "447b9a2c0c8d628169f23af6974f2b90ea013fda2144c275ab12183a9c43c4c2" } } ], "extra": [ 1, 194, 219, 15, 156, 101, 117, 191, 60, 51, 103, 44, 156, 23, 213, 90, 8, 73, 248, 157, 106, 177, 42, 119, 15, 219, 86, 217, 30, 189, 64, 37, 223, 2, 17, 0, 0, 0, 7, 105, 74, 19, 143, 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