Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34e5fad6f48042554a386b3ccbb6b60dc9493c1924b565c1ceb137c54cccc82

Tx prefix hash: 2ac7f2943823789710c5d7cec79970f5126a901c9c8946a96b223d5d41851432
Tx public key: 21a26a7cf4fbf1e8765451bf14f572b5e09dfd5431ae961cb272af2775cd6713
Timestamp: 1716685839 Timestamp [UCT]: 2024-05-26 01:10:39 Age [y:d:h:m:s]: 00:363:08:38:54
Block: 1030081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259740 RingCT/type: yes/0
Extra: 0121a26a7cf4fbf1e8765451bf14f572b5e09dfd5431ae961cb272af2775cd67130211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8779b00bb9824822aad40ab7ee6a70a0c2b618951074159050c1b8d93576e7df 0.600000000000 1498334 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": 1030091, "vin": [ { "gen": { "height": 1030081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8779b00bb9824822aad40ab7ee6a70a0c2b618951074159050c1b8d93576e7df" } } ], "extra": [ 1, 33, 162, 106, 124, 244, 251, 241, 232, 118, 84, 81, 191, 20, 245, 114, 181, 224, 157, 253, 84, 49, 174, 150, 28, 178, 114, 175, 39, 117, 205, 103, 19, 2, 17, 0, 0, 0, 3, 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