Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0bfdadb7cee16681fbde7b5085c316e0b13362ddadd06c069943d1aee122a9

Tx prefix hash: bc8176e25d4bfc7d727d9d762b09ae04bcb7f8a718c182886e26e82886a939c5
Tx public key: b2cfd055f5a35b116b0480e988c83fca879a2ce83df2a9747a51979f1d2015e9
Timestamp: 1722220545 Timestamp [UCT]: 2024-07-29 02:35:45 Age [y:d:h:m:s]: 00:228:19:23:59
Block: 1075960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163443 RingCT/type: yes/0
Extra: 01b2cfd055f5a35b116b0480e988c83fca879a2ce83df2a9747a51979f1d2015e902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a1408e83f54dc37f485009a4884db175a8119f6ca5a99aa40ecbbd36baa054 0.600000000000 1548493 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": 1075970, "vin": [ { "gen": { "height": 1075960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a1408e83f54dc37f485009a4884db175a8119f6ca5a99aa40ecbbd36baa054" } } ], "extra": [ 1, 178, 207, 208, 85, 245, 163, 91, 17, 107, 4, 128, 233, 136, 200, 63, 202, 135, 154, 44, 232, 61, 242, 169, 116, 122, 81, 151, 159, 29, 32, 21, 233, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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