Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713e1e152e8ab80334b726dfe8a20b9f0da6bb76229d899364c650b87cf8036e

Tx prefix hash: 5b64145e5b25727eae19e7fa98fe29fc49b26537556bb1fdfc8b2fbb7010f34a
Tx public key: ab4f6ba574a882dbd97bc036c37dc3ee579b1c6f9f776d362bf867ada1cb66ec
Timestamp: 1729976956 Timestamp [UCT]: 2024-10-26 21:09:16 Age [y:d:h:m:s]: 00:182:10:15:41
Block: 1140238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130190 RingCT/type: yes/0
Extra: 01ab4f6ba574a882dbd97bc036c37dc3ee579b1c6f9f776d362bf867ada1cb66ec021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76bf0a5da4dea3cd44435248dfc4c52db5aec60a68e0bd3a88f066a72aceb4a4 0.600000000000 1624033 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": 1140248, "vin": [ { "gen": { "height": 1140238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76bf0a5da4dea3cd44435248dfc4c52db5aec60a68e0bd3a88f066a72aceb4a4" } } ], "extra": [ 1, 171, 79, 107, 165, 116, 168, 130, 219, 217, 123, 192, 54, 195, 125, 195, 238, 87, 155, 28, 111, 159, 119, 109, 54, 43, 248, 103, 173, 161, 203, 102, 236, 2, 17, 0, 0, 0, 3, 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