Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76c31a4b44ae520f2dfd1eafb5fc90435c716fa2fce2ee4436e150ded273149c

Tx prefix hash: 350bcf18fb4cea223c62c4e068a7eb240336dcefed7d267f4188e0c9f9381b2a
Tx public key: 5ca05462a21eed0b1cf70e68e39af98bc88d23e5f886c23a47d4a2c75bb1439a
Timestamp: 1734347962 Timestamp [UCT]: 2024-12-16 11:19:22 Age [y:d:h:m:s]: 00:106:10:52:10
Block: 1176412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75846 RingCT/type: yes/0
Extra: 015ca05462a21eed0b1cf70e68e39af98bc88d23e5f886c23a47d4a2c75bb1439a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280eb1bda4bfad63c53763434d312a80dc092125770816127471d7b5166bafd4 0.600000000000 1662745 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": 1176422, "vin": [ { "gen": { "height": 1176412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280eb1bda4bfad63c53763434d312a80dc092125770816127471d7b5166bafd4" } } ], "extra": [ 1, 92, 160, 84, 98, 162, 30, 237, 11, 28, 247, 14, 104, 227, 154, 249, 139, 200, 141, 35, 229, 248, 134, 194, 58, 71, 212, 162, 199, 91, 177, 67, 154, 2, 17, 0, 0, 0, 5, 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