Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5268e5b98e89d76cf0bef4453fe54d42533de3d93b7a86d3d45626393c40299f

Tx prefix hash: 9c3a3d27c4771f1603492a30c7d059fa437ef9093fa8d06c5f47f7bcfc62f7a8
Tx public key: 6c91e4a7a64c70a574d9de4c95ceeeb009ceeea801118d64f0c4ae059c0f9254
Timestamp: 1708944823 Timestamp [UCT]: 2024-02-26 10:53:43 Age [y:d:h:m:s]: 01:039:19:17:55
Block: 965914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289455 RingCT/type: yes/0
Extra: 016c91e4a7a64c70a574d9de4c95ceeeb009ceeea801118d64f0c4ae059c0f92540211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc2146a2ba257e7749d8a2914bd5c609a6b5105353d4d5b66297678b10aee16c 0.600000000000 1425669 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": 965924, "vin": [ { "gen": { "height": 965914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2146a2ba257e7749d8a2914bd5c609a6b5105353d4d5b66297678b10aee16c" } } ], "extra": [ 1, 108, 145, 228, 167, 166, 76, 112, 165, 116, 217, 222, 76, 149, 206, 238, 176, 9, 206, 238, 168, 1, 17, 141, 100, 240, 196, 174, 5, 156, 15, 146, 84, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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