Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c63bed77f7ed785132488e5a86128ee4028ad976095b2f6b269d4e0db74f1851

Tx prefix hash: 9000e9e84561bf3075243516cdd51740782def9ef212dd38873d456676e85fda
Tx public key: c34edd2ad226e04507499c92d094e1bb9cd7e97277bcb3ce7fadd3bee34e43e2
Timestamp: 1694057328 Timestamp [UCT]: 2023-09-07 03:28:48 Age [y:d:h:m:s]: 01:214:20:07:13
Block: 842656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414650 RingCT/type: yes/0
Extra: 01c34edd2ad226e04507499c92d094e1bb9cd7e97277bcb3ce7fadd3bee34e43e202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.990674390000 dcy

stealth address amount amount idx
00: c3e2fe7d46d57f06c2c04ee8496c4508c9356e509e3389161a5ca2ba9bef6f25 0.990674390000 1295798 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": 842666, "vin": [ { "gen": { "height": 842656 } } ], "vout": [ { "amount": 990674390, "target": { "key": "c3e2fe7d46d57f06c2c04ee8496c4508c9356e509e3389161a5ca2ba9bef6f25" } } ], "extra": [ 1, 195, 78, 221, 42, 210, 38, 224, 69, 7, 73, 156, 146, 208, 148, 225, 187, 156, 215, 233, 114, 119, 188, 179, 206, 127, 173, 211, 190, 227, 78, 67, 226, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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