Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e63da8ac71d8d9e4ce1f7c5e58f048bb7ae7e2895a2a40510510ec7c16dee35

Tx prefix hash: 756d83269e8563abf2352170296d2bdc5410882639ae84be9082365f237127e0
Tx public key: a36242fa221b3a29eeb25639fdf65bbd0deb402f9c1be43ea2e2604dbbfa5c19
Timestamp: 1686505992 Timestamp [UCT]: 2023-06-11 17:53:12 Age [y:d:h:m:s]: 01:323:09:41:21
Block: 780134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492332 RingCT/type: yes/0
Extra: 01a36242fa221b3a29eeb25639fdf65bbd0deb402f9c1be43ea2e2604dbbfa5c19021100000001272bcc39000000000000000000

1 output(s) for total of 1.596218603000 dcy

stealth address amount amount idx
00: 2dc0e9ce385751be174bc23aec040ea3049ae61d326f1b674e7b07c6ef29e6ae 1.596218603000 1229833 of 0

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": 780144, "vin": [ { "gen": { "height": 780134 } } ], "vout": [ { "amount": 1596218603, "target": { "key": "2dc0e9ce385751be174bc23aec040ea3049ae61d326f1b674e7b07c6ef29e6ae" } } ], "extra": [ 1, 163, 98, 66, 250, 34, 27, 58, 41, 238, 178, 86, 57, 253, 246, 91, 189, 13, 235, 64, 47, 156, 27, 228, 62, 162, 226, 96, 77, 187, 250, 92, 25, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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