Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798e9796781b772a3436b8c1cf5733bd7a48e9b384f4dd9d1276183ad27d08ca

Tx prefix hash: 40862349397270000f8772e58c86e784d80cfeb03e25f288439032db887e960f
Tx public key: 261b4e4ca8cc8707244692ba16e1c3b0a331ea5cffb12dcab6c05a2fa6c08b84
Timestamp: 1582737721 Timestamp [UCT]: 2020-02-26 17:22:01 Age [y:d:h:m:s]: 04:274:07:33:15
Block: 72438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089330 RingCT/type: yes/0
Extra: 01261b4e4ca8cc8707244692ba16e1c3b0a331ea5cffb12dcab6c05a2fa6c08b840211000000164ac5aa02000000000000000000

1 output(s) for total of 353.169862003000 dcy

stealth address amount amount idx
00: 1034897aeb60d1e755f787c3655170c63458b00c69e6dc27b1efd2939b87fbd4 353.169862003000 133824 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": 72448, "vin": [ { "gen": { "height": 72438 } } ], "vout": [ { "amount": 353169862003, "target": { "key": "1034897aeb60d1e755f787c3655170c63458b00c69e6dc27b1efd2939b87fbd4" } } ], "extra": [ 1, 38, 27, 78, 76, 168, 204, 135, 7, 36, 70, 146, 186, 22, 225, 195, 176, 163, 49, 234, 92, 255, 177, 45, 202, 182, 192, 90, 47, 166, 192, 139, 132, 2, 17, 0, 0, 0, 22, 74, 197, 170, 2, 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