Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89fcbf5e83f5984a5c60d902729227f4fbee3468b88c823f45d7e315a2f77bb4

Tx prefix hash: 42ea4187ce03755e0fe3eae79bfd00f61533e0fd3e7dca1b0fb01200c7337653
Tx public key: f0ceef3d8e5a816fdb8e5809f972b42524243a4073554bb3a4e488042e028cbc
Timestamp: 1707929944 Timestamp [UCT]: 2024-02-14 16:59:04 Age [y:d:h:m:s]: 01:052:18:34:42
Block: 957473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298767 RingCT/type: yes/0
Extra: 01f0ceef3d8e5a816fdb8e5809f972b42524243a4073554bb3a4e488042e028cbc0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 592012fa0752d782016f93a3d76360a49e342c668510729ec7093f29851a204c 0.600000000000 1416791 of 15

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": 957483, "vin": [ { "gen": { "height": 957473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "592012fa0752d782016f93a3d76360a49e342c668510729ec7093f29851a204c" } } ], "extra": [ 1, 240, 206, 239, 61, 142, 90, 129, 111, 219, 142, 88, 9, 249, 114, 180, 37, 36, 36, 58, 64, 115, 85, 75, 179, 164, 228, 136, 4, 46, 2, 140, 188, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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