Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74156bae1deeadb4f56d7ff966832fb6c0c01f491b488f90fcdbc661292cfad

Tx prefix hash: d463af17ced01d44d96c7d5746b8ea64a936662d9bc8f68d925bd84662045728
Tx public key: c36f3a1dec66e2cdc5b257e9efa7cabaad6db61b3c916c5b837462a8d20fb942
Timestamp: 1648322443 Timestamp [UCT]: 2022-03-26 19:20:43 Age [y:d:h:m:s]: 03:220:00:45:55
Block: 466970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935189 RingCT/type: yes/0
Extra: 01c36f3a1dec66e2cdc5b257e9efa7cabaad6db61b3c916c5b837462a8d20fb94202110000000f2e6b1fd5000000000000000000

1 output(s) for total of 17.407435531000 dcy

stealth address amount amount idx
00: b080d405fd3329a5681e65691085076e338bcebae6c4e66c5378f83241d3b6b5 17.407435531000 885381 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": 466980, "vin": [ { "gen": { "height": 466970 } } ], "vout": [ { "amount": 17407435531, "target": { "key": "b080d405fd3329a5681e65691085076e338bcebae6c4e66c5378f83241d3b6b5" } } ], "extra": [ 1, 195, 111, 58, 29, 236, 102, 226, 205, 197, 178, 87, 233, 239, 167, 202, 186, 173, 109, 182, 27, 60, 145, 108, 91, 131, 116, 98, 168, 210, 15, 185, 66, 2, 17, 0, 0, 0, 15, 46, 107, 31, 213, 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