Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dd1469f5501b30f8131109e3b0def94f618b42c1012c97e1441eb30c704a1ce

Tx prefix hash: 2efb11dccb0d4172cd417e328dc6b4c985655e37504ffc8e4fd5c4a797ff3adf
Tx public key: b701f069711f09bb51c150d240f766c2db175ad358a481cdd32f172bc545b3ae
Timestamp: 1712529357 Timestamp [UCT]: 2024-04-07 22:35:57 Age [y:d:h:m:s]: 01:036:16:29:13
Block: 995588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287239 RingCT/type: yes/0
Extra: 01b701f069711f09bb51c150d240f766c2db175ad358a481cdd32f172bc545b3ae0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d915f44f59f51eb6b4d2d58c3aa6d9122d6fdd2eca3ca5aa649037e1506b011 0.600000000000 1455998 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": 995598, "vin": [ { "gen": { "height": 995588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d915f44f59f51eb6b4d2d58c3aa6d9122d6fdd2eca3ca5aa649037e1506b011" } } ], "extra": [ 1, 183, 1, 240, 105, 113, 31, 9, 187, 81, 193, 80, 210, 64, 247, 102, 194, 219, 23, 90, 211, 88, 164, 129, 205, 211, 47, 23, 43, 197, 69, 179, 174, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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