Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2540383d8b4271e1cfa99870c29862a4fe465714837a569ca302395e7257e69e

Tx prefix hash: 6fd380814a572b479991f5b356e0725fbe1015815fd9088b3bbdf4d27449d401
Tx public key: 2f2662ea249a1e306c00120d4df4e4fdf8ca9077b840fe0d5c1823cf901c34c5
Timestamp: 1721620078 Timestamp [UCT]: 2024-07-22 03:47:58 Age [y:d:h:m:s]: 00:259:15:24:52
Block: 1070974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185486 RingCT/type: yes/0
Extra: 012f2662ea249a1e306c00120d4df4e4fdf8ca9077b840fe0d5c1823cf901c34c5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10df47cb59ec7fa35b50c967e2081300d80a5844234096888f30e6a09208069e 0.600000000000 1543025 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": 1070984, "vin": [ { "gen": { "height": 1070974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10df47cb59ec7fa35b50c967e2081300d80a5844234096888f30e6a09208069e" } } ], "extra": [ 1, 47, 38, 98, 234, 36, 154, 30, 48, 108, 0, 18, 13, 77, 244, 228, 253, 248, 202, 144, 119, 184, 64, 254, 13, 92, 24, 35, 207, 144, 28, 52, 197, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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