Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59177e419c17b4e8b7c8651212934d8bc992a672f92c7ceadf488f2c3fcd59bb

Tx prefix hash: 845cf1fa606791a0a8be3b5bd5d11a3c2b8ed26938c40d15c37bdbbd633eb23d
Tx public key: 82b6e8e9fd6ab6daad33e0b8b4d5eb11a9456773a13c8d094755e84e2aad7f27
Timestamp: 1735786143 Timestamp [UCT]: 2025-01-02 02:49:03 Age [y:d:h:m:s]: 00:323:05:57:22
Block: 1188296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228532 RingCT/type: yes/0
Extra: 0182b6e8e9fd6ab6daad33e0b8b4d5eb11a9456773a13c8d094755e84e2aad7f27021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94540a1622f303cb70deb45cde480fc12bdc8619e7cf1cd2774d014b75b1b89c 0.600000000000 1674797 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": 1188306, "vin": [ { "gen": { "height": 1188296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94540a1622f303cb70deb45cde480fc12bdc8619e7cf1cd2774d014b75b1b89c" } } ], "extra": [ 1, 130, 182, 232, 233, 253, 106, 182, 218, 173, 51, 224, 184, 180, 213, 235, 17, 169, 69, 103, 115, 161, 60, 141, 9, 71, 85, 232, 78, 42, 173, 127, 39, 2, 17, 0, 0, 0, 4, 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