Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 693c994289f929db31d80b9a775c39ced6e9854fb80d8487d230bec9d2eed037

Tx prefix hash: 2ad16e61fab8bfa9a198be1178c759fec3d6fd8d0e4accf2fa6ddd6c77a1aaad
Tx public key: c80d56a0be339d1129886cefd271bc036fadd029717af698d5f526e5a41bc3bb
Timestamp: 1736292877 Timestamp [UCT]: 2025-01-07 23:34:37 Age [y:d:h:m:s]: 00:159:14:57:01
Block: 1192489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113813 RingCT/type: yes/0
Extra: 01c80d56a0be339d1129886cefd271bc036fadd029717af698d5f526e5a41bc3bb021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362e1daa542c12c4c963b3773ba62b5d0eb7c8752d4845f55117148c10d0acb9 0.600000000000 1679042 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": 1192499, "vin": [ { "gen": { "height": 1192489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362e1daa542c12c4c963b3773ba62b5d0eb7c8752d4845f55117148c10d0acb9" } } ], "extra": [ 1, 200, 13, 86, 160, 190, 51, 157, 17, 41, 136, 108, 239, 210, 113, 188, 3, 111, 173, 208, 41, 113, 122, 246, 152, 213, 245, 38, 229, 164, 27, 195, 187, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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