Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdd6ddad4a4fa0f08071cca426c803d48a5587d277bc7d9c7e55daeb5666258

Tx prefix hash: c6972dd63ed20f193c95aced8945d3207d904d9d2b5af9230da828347b635e61
Tx public key: a178c515126c253f7b8dc545d9bc99b2a02dc9d9ae8d4252bce297f513e7171a
Timestamp: 1712092076 Timestamp [UCT]: 2024-04-02 21:07:56 Age [y:d:h:m:s]: 00:171:15:33:28
Block: 991968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122986 RingCT/type: yes/0
Extra: 01a178c515126c253f7b8dc545d9bc99b2a02dc9d9ae8d4252bce297f513e7171a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c16db95e6c43f925adf88893b78d6e90ae1a8a12920ab89c9e5a908bd5af1d7 0.600000000000 1452304 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": 991978, "vin": [ { "gen": { "height": 991968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c16db95e6c43f925adf88893b78d6e90ae1a8a12920ab89c9e5a908bd5af1d7" } } ], "extra": [ 1, 161, 120, 197, 21, 18, 108, 37, 63, 123, 141, 197, 69, 217, 188, 153, 178, 160, 45, 201, 217, 174, 141, 66, 82, 188, 226, 151, 245, 19, 231, 23, 26, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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