Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e49bcb6d27fc0469e4149e02dd6f892880aa659fb343552939a168777a3ab815

Tx prefix hash: 4088d40fe568f04f0364fffd20111b662e4b8578aadffb1b6d17026764d32c80
Tx public key: 7ce4c2a327b15e64c46079a362a5557ff133dcb6b5a02a6554e15c991ea89a1a
Timestamp: 1706907979 Timestamp [UCT]: 2024-02-02 21:06:19 Age [y:d:h:m:s]: 00:286:06:17:24
Block: 949001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204967 RingCT/type: yes/0
Extra: 017ce4c2a327b15e64c46079a362a5557ff133dcb6b5a02a6554e15c991ea89a1a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17f0b6fb370acdd24ea43ca07aaaf8b1a7f0b5641497bb57f98f561d2a834814 0.600000000000 1407523 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": 949011, "vin": [ { "gen": { "height": 949001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17f0b6fb370acdd24ea43ca07aaaf8b1a7f0b5641497bb57f98f561d2a834814" } } ], "extra": [ 1, 124, 228, 194, 163, 39, 177, 94, 100, 196, 96, 121, 163, 98, 165, 85, 127, 241, 51, 220, 182, 181, 160, 42, 101, 84, 225, 92, 153, 30, 168, 154, 26, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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